* add ffe server sdk landing page and stubs for each language

* add to sidebar

* poll

* simpler setup

* rebuild nav structure

also:
- rename `setup` to `client`
- update links, other URL references

* add tile layout for server landing page

+ also renames the tile partial in the client page for consistency

* add go docs for openfeature implementation (#33234)

* add go docs for openfeature implementation

* add docs for blocking init, custom timeout, non blocking

* no agent version

* Documentation for dd-trace with feature flagging support (#33165)

* Documentation for dd-trace with feature flagging support

* Update content/en/feature_flags/setup/nodejs.md

Co-authored-by: Leo Romanovsky <leo.romanovsky@datadoghq.com>

---------

Co-authored-by: Leo Romanovsky <leo.romanovsky@datadoghq.com>

* Add Ruby feature flags documentation (#33233)

* Add Ruby feature flags server documentation

- Port content from setup/ruby.md to server/ruby.md
- Maintain all Vale linting fixes from previous commits
- Include prerequisites, installation, usage examples, and troubleshooting
- Support for boolean, string, number, object flags and evaluation context

* Update content/en/feature_flags/server/ruby.md

Co-authored-by: Leo Romanovsky <leo.romanovsky@datadoghq.com>

---------

Co-authored-by: Leo Romanovsky <leo.romanovsky@datadoghq.com>

* Add python documentation for OpenFeature implementation (#33247)

* consolidate duplicate files

Files were in two different paths (older `setup` path and newer `server` path)

* Add Java Feature Flags Setup Documentation (#33194)

* Add Java Feature Flags setup documentation

- Add comprehensive Java SDK onboarding guide
- Include installation instructions for Maven and Gradle
- Document OpenFeature provider initialization and usage
- Add code examples for all flag types (boolean, string, int, double, object)
- Document error handling and common error codes
- Include best practices and troubleshooting guide
- Add Java to feature flags setup page navigation
- Document integration with Datadog APM and exposure tracking

Related: FFE Server SDK code freeze preparation

* fix(docs): Add missing bootstrap JAR and improve Java Feature Flags documentation

Critical fixes:
- Add missing dd-java-agent-feature-flagging-bootstrap dependency to all examples
- Add Building from Source section with detailed instructions
- Explain bootstrap module purpose (classloader communication)
- Add troubleshooting for ClassNotFoundException

Improvements to match Java APM documentation patterns:
- Add application server configuration tabs (Spring Boot, Tomcat, JBoss, Jetty, Docker)
- Update all code examples to use SLF4J logger instead of System.out/err
- Add Compatibility requirements section
- Add Getting started section
- Update initialization example to show complete application structure

Code quality:
- Use logger.info/warn/error throughout with parameterized messages
- Show proper exception handling with logger
- Match actual implementation in ffe-dogfooding repo
- Include named client usage ("my-app")

The documentation now accurately reflects the required dependencies,
follows established Datadog docs patterns, and provides complete
setup instructions for the development build.

* docs(java): Improve documentation based on review feedback

Changes:
- Add cross-linking to Configuration section from early warning
- Add OpenFeature SDK to compatibility requirements (it is required)
- Remove all local build instructions (only reference published X.X.X versions)
- Add skip guidance for users with existing agent/remote-config setup
- Clarify ProviderNotReadyError is OpenFeature exception (optional handling)
- Update exception handling to be optional based on availability requirements
- Note that not catching exception may prevent application startup

Improvements:
- Users with existing APM can skip to provider initialization
- Users with existing remote-config can skip agent configuration
- Clear guidance on when exception handling is optional vs required
- Removed all references to building from source

* docs(java): Add event state watching and clarify provider instance sharing

Changes:
- Add PROVIDER_ERROR and PROVIDER_STALE event listeners to async init example
- Note that PROVIDER_CONFIGURATION_CHANGED is optional (depends on provider support)
- Update multiple clients section: "organize context and flags" (not just flags)
- Clarify that Provider instance is shared globally (client names are organizational only)

The Provider constructor doesn't take a name parameter - it's a single shared instance.
Named clients are just for organizing your application code, not separate providers.

* docs(java): Align flag keys and attributes with mobile SDK conventions

Changes:
- Update all flag keys to use dot notation (matching Android/iOS):
  * new-checkout-flow -> checkout.new
  * ui-theme -> ui.theme
  * payment-api-endpoint -> payment.api.endpoint
  * max-retries -> retries.max
  * discount-rate -> pricing.discount.rate
  * feature-config -> ui.config
  * All other flags updated to dot notation

- Standardize attribute to use "tier" consistently (not "plan")

- Remove "country" attribute from basic example to match mobile simplicity

This creates consistency across all SDK documentation and makes it easier
for users to migrate between platforms or reference examples.

* fix tile image, add page to side nav

* headings: sentence-case capitalization

* style linter, general style edits

* Add Java Feature Flags setup documentation

- Add comprehensive Java SDK onboarding guide
- Include installation instructions for Maven and Gradle
- Document OpenFeature provider initialization and usage
- Add code examples for all flag types (boolean, string, int, double, object)
- Document error handling and common error codes
- Include best practices and troubleshooting guide
- Add Java to feature flags setup page navigation
- Document integration with Datadog APM and exposure tracking

Related: FFE Server SDK code freeze preparation

* fix(docs): Add missing bootstrap JAR and improve Java Feature Flags documentation

Critical fixes:
- Add missing dd-java-agent-feature-flagging-bootstrap dependency to all examples
- Add Building from Source section with detailed instructions
- Explain bootstrap module purpose (classloader communication)
- Add troubleshooting for ClassNotFoundException

Improvements to match Java APM documentation patterns:
- Add application server configuration tabs (Spring Boot, Tomcat, JBoss, Jetty, Docker)
- Update all code examples to use SLF4J logger instead of System.out/err
- Add Compatibility requirements section
- Add Getting started section
- Update initialization example to show complete application structure

Code quality:
- Use logger.info/warn/error throughout with parameterized messages
- Show proper exception handling with logger
- Match actual implementation in ffe-dogfooding repo
- Include named client usage ("my-app")

The documentation now accurately reflects the required dependencies,
follows established Datadog docs patterns, and provides complete
setup instructions for the development build.

* docs(java): Improve documentation based on review feedback

Changes:
- Add cross-linking to Configuration section from early warning
- Add OpenFeature SDK to compatibility requirements (it is required)
- Remove all local build instructions (only reference published X.X.X versions)
- Add skip guidance for users with existing agent/remote-config setup
- Clarify ProviderNotReadyError is OpenFeature exception (optional handling)
- Update exception handling to be optional based on availability requirements
- Note that not catching exception may prevent application startup

Improvements:
- Users with existing APM can skip to provider initialization
- Users with existing remote-config can skip agent configuration
- Clear guidance on when exception handling is optional vs required
- Removed all references to building from source

* docs(java): Add event state watching and clarify provider instance sharing

Changes:
- Add PROVIDER_ERROR and PROVIDER_STALE event listeners to async init example
- Note that PROVIDER_CONFIGURATION_CHANGED is optional (depends on provider support)
- Update multiple clients section: "organize context and flags" (not just flags)
- Clarify that Provider instance is shared globally (client names are organizational only)

The Provider constructor doesn't take a name parameter - it's a single shared instance.
Named clients are just for organizing your application code, not separate providers.

* docs(java): Align flag keys and attributes with mobile SDK conventions

Changes:
- Update all flag keys to use dot notation (matching Android/iOS):
  * new-checkout-flow -> checkout.new
  * ui-theme -> ui.theme
  * payment-api-endpoint -> payment.api.endpoint
  * max-retries -> retries.max
  * discount-rate -> pricing.discount.rate
  * feature-config -> ui.config
  * All other flags updated to dot notation

- Standardize attribute to use "tier" consistently (not "plan")

- Remove "country" attribute from basic example to match mobile simplicity

This creates consistency across all SDK documentation and makes it easier
for users to migrate between platforms or reference examples.

* docs(java): Move Java Feature Flags docs to server/ directory

- Move java.md from feature_flags/setup/ to feature_flags/setup/server/
- Update frontmatter to reference server-side landing page
- Apply style edits from linter (sentence-case headings, consistent capitalization)

* extra dev info

* various style edits

* section collapsing

* better sections

* reduce expanders

---------

Co-authored-by: Joe Peeples <joe.peeples@datadoghq.com>

* remove Java from client-side tile partial

* Python review edits

also applied to other languages with the same text

* Ruby review edits

and other languages with same text

* Go review edits

and other languages with same text

* Node.js review edits

+ other languages

* clean up links

---------

Co-authored-by: Joe Peeples <joe.peeples@datadoghq.com>
Co-authored-by: Greg Huels <greg.huels@gmail.com>
Co-authored-by: Sameeran Kunche <sameeran.kunche@datadoghq.com>
Co-authored-by: Oleksii Shmalko <oleksii.shmalko@datadoghq.com>
Co-authored-by: Tyler Potter <tyler.potter@datadoghq.com>